Open two terminal shells:

 In Terminal 1

1. telnet mvc-dmo1-rf (dorado1 user and pass)
2. cd auv-qnx
3. (. configSrc) - no configSrc in auv-qnx
4. echo $AUV (verify /home/dorado1/auv-qnx/auv/altex/onboard)
5. qtalk -m /dev/ser13
   1. !a<enter>   (to turn on TREX2 cpu, you'll see GulperSolenoidFB = 1)
   2. ctrl-a x   (to exit)
6. cd $AUV/bin
7. < pause> and follow procedure in Terminal 2 below
8. nohup ./vcsServer -v &
9. ps -a 
10. Go to terminal 2 and launch amc_o_rt
11. ps-a (after amc_o_rt starts, you should see the processes of auv-qnx spawned.
12. to terminate by force:   slay supervisor   slay vcsServer
    

In Terminal 2

1. slogin dorado1@trex2
2. cd amc
3. . config.amc
4. cd mission
5. cat init.cfg (check depth envelop, check mission time in seconds)
6. <Pause and Go to Terminal 1 and launch vcsServer>
7. nohup ../exec/amc_o_rt science4.cfg &
8. cd ~/amc/log/latest
9. tail -f TREX.log   ( it takes about 30 seconds or so to start and then lots of activity, should be no error or 'relax' in the stream of log messages)
10. go to terminal 1
11. to terminate by force:   killall amc_o_rt

when the vehicle has surfaced, to check for gulpers (not required, but if you are bored and want to see)

1. slogin dorado1@trex2
2. cd amc
3. . config.amc 
4. ./bin/signal_process.hsh  (returns how many gulpers have fired, how far it is in transect, if signal is below 0.045 then it will be low res transect of 1Km, if above 0.12 it is high res 500m separation, if in between 750m)